Method for mobile service chaining via hybrid network resources switching

ABSTRACT

A method includes receiving a request for a communication session from a user device, identifying a first resource from a plurality of resources, wherein the first resource is associated with a first service control layer for a radio access network and wherein the plurality of resources includes at least one virtual network function (VNF), identifying a second resource from the plurality of resources, wherein the second resource is associated with a second service control layer for LTE core functions, identifying a third resource from the plurality of resources, wherein the third resource is associated with a third service control layer for content delivery, allocating a virtual machine to be used to instantiate the at least one VNF, instantiating the at least one VNF and establishing the communication session by facilitating communications between the first service control layer, the second service control layer and the third service control layer.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of, and claims priority to, U.S.patent application Ser. No. 15/383,719, filed Dec. 19, 2016, entitled“Method For Mobile Service Chaining Via Hybrid Network ResourcesSwitching,” the entire contents of which are hereby incorporated hereinby reference.

TECHNICAL FIELD

This disclosure relates generally to network management and, morespecifically, to assigning and configuring general purpose hardware tosupport virtual network functions.

BACKGROUND

Communication networks have migrated from using specialized networkingequipment executing on dedicated hardware, like routers, firewalls, andgateways, to software defined networks (SDNs) executing as virtualizednetwork functions (VNF) in a cloud infrastructure. To provide a service,a set of VNFs may be instantiated on the general purpose hardware. EachVNF may require one or more virtual machines (VMs) to be instantiated.In turn, VMs may require various resources, such as memory, virtualcomputer processing units (vCPUs), and network interfaces or networkinterface cards (NICs). Determining how to assign these resources amongVMs in an efficient manner may be unbearably complex.

This disclosure is directed to solving one or more of the problems inthe existing technology. A service chain in LTE/LTE-A networks mayinvolve a combination of hybrid physical network functions (PNF)/VNFbased network application functions that are interconnected together viamultiple control plane interfaces to form a service based sessionconstruct prior to delivering service specific user data. The hybridPNF/VNF network functions and their distinctive network managementsystems, as well as their deployment in a vertically pooled resourceconfiguration, presents a complex network architecture that needs to bemanaged effectively.

SUMMARY

The present disclosure includes a method including receiving a requestfor a communication session from a user device, identifying a firstresource from a plurality of first resources, wherein the first resourceis associated with a first service control layer for a radio accessnetwork and wherein the plurality of resources includes at least onevirtual network function (VNF), identifying a second resource from theplurality of second resources, wherein the second resource is associatedwith a second service control layer for LTE core functions, identifyinga third resource from the plurality of third resources, wherein thethird resource is associated with a third service control layer forcontent, allocating a virtual machine to be used to instantiate the atleast one VNF, instantiating the at least one VNF, establishing thecommunication session using the first resource, the second resource andthe third resource by facilitating communications between the firstservice control layer, the second service control layer and the thirdservice control layer. The method may further wherein the plurality ofsecond resources comprises a combination of virtual network functionsand physical network functions chained together in communication witheach other. The method may further include wherein the second servicecontrol layer for LTE core functions allocates the plurality of secondresources to provide LTE services and may further include tracking aperformance metric for the communication and adjusting the plurality ofsecond resources to provide LTE services.

In an aspect, the method may further include Identifying virtualmachines (VMs) to be used to instantiate the at least one VNF,identifying hardware resources to be consumed by the VMs, determining asession capacity for a hardware platform based on the hardware resourcesand performance requirements, and assigning the hardware resources ofthe hardware platform to at least one of the VMs. The hardware resourcesmay include a virtual computer processing unit (vCPU), a networkinterface card (NIC), and computer memory. In an aspect, the performancerequirements may change during the communication session and thedetermining step may include determining a second session capacity forthe hardware platform and the assigning step may include dynamicallyadjusting the hardware resources assigned to support the second sessioncapacity.

In an aspect, the receiving step comprises receiving the request for acommunication session from an application service layer and the requestfor a communication includes performance metrics for the communication.The method may further include tracking a performance of thecommunication and dynamically adjusting a capacity of the secondresource based on the tracking step

The disclosure is also directed to a system including an access networkhaving a first service control layer associated therewith, a combinationof virtual network resources and physical network resources, wherein thevirtual network resources and physical network resources arecommunicatively chained to provide a dynamically configurable set ofresources and wherein the combination matrix has a second servicecontrol layer associated therewith, a content network having a thirdservice control layer associated therewith; and a master serviceorchestration layer in communication with the first service controllayer, the second service control layer and the third service controllayer, the service orchestration layer having a processor and a memorycomprising executable instructions, wherein the executable instructionscause the processor to effectuate operations, the operations includingreceiving a request for a communication session, receiving a set ofperformance metrics for the communication session, sending to the firstservice control layer a request to allocate network access resources tosupport the communication session, sending to the second service controllayer a request to allocate virtual network resources or physicalnetwork resources to support the communication session, sending to thethird service control layer a request to aggregate content to beprovided during the communication session and monitoring thecommunication session.

In an aspect the operations may further include sending a request to thefirst service control layer to dynamically adjust the allocation ofnetwork access resources based on the monitoring step. The method mayfurther include sending a request to the second service control layer todynamically adjust the allocation of virtual network functions orphysical network functions based on the monitoring step.

In an aspect, the service orchestration layer is in communications withan application service layer and wherein the request for a communicationsession and the set of performance metrics is received from theapplication service layer. The request for communication is request forone of a broadcast, multicast and unicast communication. In an aspectwherein the communication is a broadcast communication, the allocatednetwork resources, the allocated virtual network functions and physicalnetwork functions support multiple user equipment participating in thecommunication session. The performance metrics may include end userquality of service and network throughput associated with thecommunication session. The operations further include coordinatingdynamically reallocation of resources during the communication session.The operations may further include receiving from the third servicecontrol layer additional content generated during the communicationsession and sending a second request to the second control layer todynamically reallocate resources to support the communication session.

In an aspect, the operations may further include maintaining a mappingtable of connected user equipment and contexts associated with thecommunication session. The operations further include providingcoordination between the first service control layer, the second servicecontrol layer and the third service control layer during thecommunication session.

BRIEF DESCRIPTION OF THE DRAWINGS

In the following description, for purposes of explanation, numerousspecific details are set forth in order to provide an understanding ofthe variations in implementing the disclosed technology. However, theinstant disclosure may take many different forms and should not beconstrued as limited to the examples set forth herein. Where practical,like numbers refer to like elements throughout.

FIG. 1a is a representation of an exemplary network.

FIG. 1b is a representation of an exemplary hardware platform for anetwork.

FIG. 2a is a representation of an exemplary embodiment in accordancewith the present disclosure;

FIG. 2b is a representation of an exemplary embodiment illustrating thechaining of VNF in accordance with the present disclosure.

FIG. 3a is an exemplary flow diagram showing the allocation of hardwareresources to support virtual machines in accordance with the presentinvention.

FIG. 3b is an exemplary flow diagram showing the allocation of resourcesin accordance with the present disclosure.

FIG. 3c is an exemplary flow diagram showing the dynamic allocation ofresources in accordance with the present disclosure.

FIG. 4 depicts an exemplary communication system that provide wirelesstelecommunication services over wireless communication networks that maybe at least partially implemented as an SDN.

FIG. 5 depicts an exemplary diagrammatic representation of a machine inthe form of a computer system.

FIG. 6 is an exemplary diagrammatic representation of a cellularcommunications network.

FIG. 7 is an example system including RAN and core network functions.

FIG. 8 depicts an overall block diagram of an example packet-basedmobile cellular network environment.

FIG. 9 illustrates an architecture of a typical GPRS network

FIG. 10 illustrates a PLMN block diagram view of an example architecturethat may be replaced by a telecommunications system

DETAILED DESCRIPTION

This disclosure is directed to the efficient management of a hybridPNF/VNF network in a vertically pooled resource configuration. Dynamicswitching of these network functions across hybrid PNF/VNF resourcepools is disclosed to maintain session constructs and for efficientservices delivery. The digital mobile service and media experience insuch a hybrid environment is influenced by various factors includingcontent computing infrastructure (creation, aggregation anddistribution), network infrastructure (data transport, connectivity, enduser service delivery options) and digital experience (use ofsmartphones, PDAs, digital home equipment, mobility, convergence etc.).

The disclosure includes an intelligent tiered service orchestrationlayer for such a massive cloud centric network infrastructure withhybrid PNF/VNF components across multiple networking domains. The tieredorchestration layer works vertically across the network infrastructurechain (PNF/VNF) and horizontally across the networking/applicationsdomain within an end to end service delivery path can help in designingand developing an end-to-end service chain that is effective fortracking user level services consumption, preferences and use suchinformation via integrated closed loop monitoring method within theservice layer to personalize the end users mobile services experience.Such an approach could lead to targeted new revenue generation,management and dynamic pricing for digital mobile services. Thisdisclosure provides a method to provide such a service layerorchestrator that can work both vertically and horizontally across theVNFs, service domains, chaining them for a given service type,monitoring the status and utilize the pooled VNF resources effectivelyto deliver a robust service to end user

FIG. 1a is a representation of an exemplary network 100. Network 100 maycomprise an SDN that is, network 100 may include one or more virtualizedfunctions implemented on general purpose hardware, such as in lieu ofhaving dedicated hardware for every network function. That is, generalpurpose hardware of network 100 may be configured to run virtual networkelements to support communication services, such as mobility services,including consumer services and enterprise services. These services maybe provided or measured in sessions.

A virtual network functions (VNFs) 102 may be able to support a limitednumber of sessions. Each VNF 102 may have a VNF type that indicates itsfunctionality or role. For example, FIG. 1a illustrates a gateway \INF102 a and a policy and charging rules function (PCRF) VNF 102 b.Additionally or alternatively, VNFs 102 may include other types of VNFs.Each VNF 102 may use one or more virtual machines (VMs) 104 to operate.Each VM 104 may have a VM type that indicates its functionality or role.For example, FIG. 1a illustrates a MCM VM 104 a, an ASM VM 104 h, and aDEP VM 104 c. Additionally or alternatively, VMs 104 may include othertypes of VMs. Each VM 104 may consume various network resources from ahardware platform 106, such as a resource 108, a virtual centralprocessing unit (vCPU) 108 a, memory 108 b, or a network interface card(NIC) 108 c. Additionally or alternatively, hardware platform 106 mayinclude other types of resources 108.

While FIG. 1a illustrates resources 108 as collectively contained inhardware platform 106, the configuration of hardware platform 106 mayisolate, for example, certain memory 108 c from other memory 108 c. FIG.1b provides an exemplary implementation of hardware platform 106 whichwill be discussed in more detail below.

With respect to FIG. 2, there is shown a hybrid network system 200having both VNFs and physical hardware functions PNFs which may, forexample, include hardware and software from a plurality of vendors.There is shown a box 220 representing hardware platform(s) 106, whichmay, for example, include one or more hardware platforms. The hardwareplatforms 106 may be generic hardware servers capable of beingconfigured using software to provide processing for one or more VNFs. Assuch, one or more VNFs may be instantiated on one or more hardwareplatform(s) 106 dynamically as needed for supplying networkfunctionality for communications involving user elements 211.

The hardware platform(s) 106 may be in communication with virtualswitches 218 which in turn are in communication with a pool of VMs 214,which, as shown in this example, include VM1 214 a, VM2 214 b, and VMn214 n where n can represent any number of virtual machines. The virtualswitches 218 assist in the mapping of one or more entities in the poolof VMs 214 to the hardware platform(s) 106 that are represented by box220. For example, an MME function may be instantiated as a VNF on bothVM1 214 a and VM2 214 b and therefore require switching capabilityduring a communication session. Using virtual switches 218 for thisfunctionality may provide more flexibility in dynamically configuringthe VNFs used to support the various communication sessions.

Also shown is a radio access network (RAN) function 212 which may, forexample, comprise RAN hardware from one or more vendors. The RANfunction 212 is in communication with the RAN service control lawyer 206which may, for example, include the setup and allocation of RANresources for a particular LTE communication requested by user equipment211. While FIG. 2 shows a RAN network function 212, the network may beany type of access network, including but not limited to 5G, Wi-Fi,Bluetooth, WAN, LAN, or any other type of network. The term accessnetwork function and RAN network function as used herein areinterchangeable.

There is also shown a content network 216 which may, for example,include the functions to create, aggregate, and distribute content for acommunication requested by LIE 211. The RAN function 212 is incommunication with the content network 216 through the pool of virtualmachines 214 as indicated by a series of arrow(s) 213. The series ofarrows 213 are shown passing through the pool of VMs 214 to indicatethat the network functionality to support the communication session,including by not limited to MME, HSS, gateways, and other networkfunctionality is provided by one or more hardware or software definednetwork elements.

There is also shown a series of service control layers. There is anetwork access service control layer 206 associated with the accessnetwork function 212. The network access control layer 206 may be amiddleware layer that provides secure access to the RAN function 212,including, but not limited to, configuring RAN resources to enable theLTE bearer and service establishment in a LTE, context. The networkaccess service control layer 206 may control both the physical networkaccess resources as well as SDN controlled access network resources andprovides the vertical chaining of resources to establish a UE contextfor the provision of services.

Another control layer is the LTE core service control layer 208. ThisLTE core service control layer 208 provides instantiation, access andcontrol to the various virtual functions running on virtual machines VM1214 a through VMn 214 n. There may also be physical network functions(PNFs) under the control of the LIE core service control layer. As such,the LTE core service control layer is configured to manage a hybridmatrix of VNFs and PNFs comprising the LTE core network functionality.Finally, there is a content service control layer 210 which providesAPIs to access the content network 216. Each of the LTE core servicecontrol layer 208 and the content service control layer 210 provides thevertical chaining of resources associated therewith.

In order to control the horizontal chaining of resources, there is showna master service orchestrator layer 202. The master service orchestratorlayer 202 coordinates resource allocation and management acrossdisparate access network and LTE core network functions. This providesdynamic and agile in-field end to end services testing utilizing hybridnetwork functions.

The master service orchestrator layer 202 also allows for quickturn-around times for completion of new services by providing an accesspoint to UE 211. The master service orchestrator layer 202 may interworkdirectly with UE 211, via integrated software agents where necessary, ondemand for a given application or service to extract certain criticalperformance metrics that may be used in the cross-layer correlation withthe access network control layer 206 and the content service controllayer 210 for customization or personalization based on network and userdynamics when interacting with the customers' UE 211 for a given mobileservice that was chained in a certain manner.

With reference to FIG. 2h , there is shown a functional matrix 314 ofhybrid VNFs and PNFs that comprise the LTE core functions. For example,MME pools 320 comprising VNFs and PNFs from multiple vendors A and B maybe included. Likewise, HSS pools 322 comprising VNFs and PNFs frommultiple vendors A and B may be included. S/PGW pools 324 comprisingVNFs and PNFs from multiple vendors A and B may be included. MGW pools326 comprising VNFs and PNFs from multiple vendors A and B may beincluded. Finally, broadcast/multicast service center (BMSC) pools 328comprising VNFs and PNFs from multiple vendors A and B may be included.Note that these LTE core functions represented in FIG. 2b are exemplaryand non-limiting and other LIE core network functions, either virtual orphysical, are included within the scope of the present disclosure.

The master service orchestrator layer 202 may also provide instructionsand feedback to the LTE core service control layer 208 to enable thedynamic instantiation of the functional matrix 314 of VNF/PNF LTE coreelements. Based on feedback from the master service orchestrator layer202, the LTE core service control layer 208 may dynamically instantiatea number of \TNF elements such as encoders of a given type, perform rateadaptation to meet a given service profile, invoke compression oracceleration schemes, or any other adaptations for faster packetprocessing in the network or to meet other class of servicerequirements. As shown in FIG. 2h , the functional matrix 314 may bedynamically modified to change the boundaries between physical andvirtual network elements. The LTE core service control layer 208maintains the state tables required to synchronize the UE mobilitycontext and bearer management across the functional matrix 314 for anyparticular communication session or sessions.

The master service orchestrator layer 202 also interfaces with theapplication service layer 201 on a per service chain or applicationbasis and extracts the relevant network requirements as well as theapplication service layer 201 performance metrics that are important tocross-layer correlation at the master service orchestrator layer 202.The application service layer 201 may provide the master serviceorchestrator layer 202 with source content metrics used a baselinereference for certain applications for proactive evaluation and eventhandling.

The application service layer 201 may also interact directly with UE 211to develop performance metrics that may be used on the cross-layercorrelation through the master service orchestration layer 202 with theaccess network layer 206, the content layer 210 and the LTE core servicelayer 208. This permits the customization or personalization based onnetwork and user dynamics when interacting with a customer for any givenmobile service.

Additionally, the architecture shown in FIGS. 2a and 2b permit thedynamic and agile in-field end-to-end services testing utilizing thehybrid physical/virtual network functions that demand quick turnaroundfor completion. This is useful for preparation and launch of commercialservices, including applications relating to the machine to machinecommunications, the Internet of Things (IoT), services provided bymultiple providers, device and network state determination and otherapplications.

FIG. 3a shows an exemplary flow chart of how the virtual networkelements identified in FIG. 2b may be assigned. At 330, the VMs to beused to instantiate VNFs are identified. At 331, the hardware resourcesto be consumed by the VMs are identified. At 332, the sessionrequirements are identified. Finally, at 333, the hardware resources areassigned to the VMs.

Use Cases. The tiered master service orchestrator 202 at the networkcontrol layer works across the horizontal and vertical resource pools inan end-to-end call setup during critical resources allocation phase andchains an end user or group of users for proper session/associatedbearer establishments associated with any cast mobility service,including, for example, unicast, broadcast and multicast services.

As an example for the broadcast service scenario, the content network216 has its own content service control layer 210 for the creation,aggregation and distribution of content. A user through the UE 211 mayhave previously established a request a particular type of broadcastservice to be provided by the content network 216. As part of the startof the broadcast, there is a request passed through either theapplication service lawyer 201 or directly to the master serviceorchestrator 202. In either case, the request for service is passed tothe master service orchestrator layer 202 which then may interwork withthe LIE core service control layer 208 and the access network servicecontrol layer 206 to determine the specific content type, audio/videoencoding and/or compression schemes, algorithms and accelerationmechanisms that may be needed for preparing the content format to bedelivered via broadcast to the end users based on available networkcapacity, user demand, service offering, subscription and geographiclocation needs. Based on the feedback received from serviceorchestrator, the VNF service control layer 208 can dynamicallyinstantiate the required type and number of PNF/VNF elements 320, 322,324, 326, 328 such as encoders of a given type, perform rate adaptationto meet a given service profile or class of service and/or invokecompression/acceleration schemes for faster packet processing in thenetwork. The master services orchestration layer 201 and the applicationservice layer 202 may work in tandem on a per service chain or perapplication basis to extracts the relevant network requirements andassign and/or instantiate the PNF/sVNFs to support the communicationrequest. The application service layer 201 provides the master serviceorchestrator layer 202 with source content metrics that are used as abaseline reference for certain applications for proactive evaluation andevent handling for customization.

A similar process occurs in the case in which a UE 211 initiates arequest for service which may, for example, include a request forcontent. With reference to FIG. 3a , there is shown an exemplary methodfor providing a service requested by a UE 211. At 350, there is arequest from the UE 211 to establish a communication session. Thatrequest may be sent to the application service layer 201 or directly tothe master service orchestrator layer 202. At 351, the access networkresources are determined. As set forth earlier, access network resourcesmay include RAN resources from one or more vendors as well as otherresources for other access network types including, for example, Wi-Fior Bluetooth. These network resources may be determined in communicationwith the access network services control layer 206. At 352, the LTE coreresources are determined. The LTE core resources may be a hybrid ofPNFs/VNFs to provide the core resources for processing the communicationand may, for example, be determined by the LTE core service controllayer 208. At 353, the content delivery resources are identified. Theseresources are based on specific content requested by the UE 211 or, inthe case of broadcast, by the content requested to be broadcast to aplurality of UEs 211. The content resources may be determined by thecontent service control layer 210. At each of steps 351, 352 and 353,the application service layer 201, which monitors the end userexperience, including any personalization, QoS considerations or anyother aspects of the user experience, in conjunction with the masterservice orchestrator layer 202, which monitors the use of all accessnetwork, LTE core functions, and content determines the requirements forthe communication and communicates with the lower service control layersto allocate the resources identified. At 354, the identified resourcesare assigned and VNFs, if any, are instantiated. At 355, thecommunication is established.

For any particular communication, for example, a communicationassociated with IoT, the resources required for the delivery of thecommunication services may change over time. As such, the master servicelevel orchestrator 202, which is monitoring the state of the chainedresources both vertically and horizontally, is able to dynamicallycontrol the allocation/deallocation of the resources used for thecommunication.

Another example of a process flow is shown in FIG. 3c in which contentis to be delivered to a user or multiple users. At 360, the content typeis determined, which may, for example be content that can be monetizedfor particular applications. At 361, the QoS and other performancerequirements may be determined by the application service control layer201 and passed to the master services orchestration layer 202. At 362.The current state of network resources, including access networkresources, LTE core network resources and content network resourceswhich are monitored by the master services orchestration layer 202, aredetermined. At 363, a request for additional resources for delivery ofthe content is requested by the master service orchestration layer toeach of the access network service control layer 206, the LTE coreservice control layer 208 and the content service control layer 210 asmay be needed. At 364, the requested resources are allocated and at 365the communication is established and monitored. At 366, a decision ismade as to whether more resources are needed to meet performancemetrics, if yes, the process returns to 362 to start the process ofdynamically allocating more resources. If no more resources are neededat 366, the decision as to whether less resources are needed to continueto meet the performance metrics. If yes, resources are deallocated at368. If no more resources are needed or if resources are deallocated,then the process returns to 365 to continue to monitor the communicationsession to enable the allocation of resources acceptable to meet theperformance metrics.

It should be understood that these process flows are exemplary only andare not intended to limit the disclosure or the scope of the appendedclaims in any way.

By tracking the hybrid PNF/VNF network resources, their connectivitymappings between the mobility access and core network elements as wellas between the mobility core and content delivery network functions in aservice chain that are pooled in a matrix configuration, the two tierslayered orchestrators comprising the application service layer 201 andthe master service level orchestrator 202 can determine the bestpossible means of sharing such resource pools for the specific mobileservice chain based on the aggregate services offering, networkconditions, health of the service chain and end users' servicecommitments and needs. In such a mobile service chained environment thatuses a structured and tiered orchestrator, customer experience andservice personalization could be significantly improved.

To complete the description of the operating environment, with respectto FIG. 1b , there is shown a hardware platform 106 comprising one ormore chasses 110. Chassis 110 may refer to the physical housing orplatform for multiple servers or other network equipment. In an aspect,chassis 110 may also refer to the underlying network equipment. Chassis110 may include one or more servers 112. Server 112 may comprise generalpurpose computer hardware or a computer. In an aspect, chassis 110 maycomprise a metal rack, and servers 112 of chassis 110 may comprise bladeservers that are physically mounted in or on chassis 110.

Each server 112 may include one or more network resources 108, asillustrated. Servers 112 may be communicatively coupled together (notshown) in any combination or arrangement. For example, all servers 112within a given chassis 110 may be communicatively coupled. As anotherexample, servers 112 in different chasses 110 may be communicativelycoupled. Additionally or alternatively, chasses 110 may becommunicatively coupled together (not shown) in any combination orarrangement.

The characteristics of each chassis 110 and each server 112 may differ.For example, FIG. 1b illustrates that the number of servers 112 withintwo chasses 110 may vary. Additionally or alternatively, the type ornumber of resources 110 within each server 112 may vary. In an aspect,chassis 110 may be used to group servers 112 with the same resourcecharacteristics. In another aspect, servers 112 within the same chassis110 may have different resource characteristics.

Given hardware platform 106, the number of sessions that may beinstantiated may vary depending upon how efficiently resources 108 areassigned to different VMs 104. For example, assignment of VMs 104 toparticular resources 108 may be constrained by one or more rules. Forexample, a first rule may require that resources 108 assigned to aparticular VM 104 be on the same server 112 or set of servers 112. Forexample, if VM 104 uses eight vCPU's 108 a, 1 GB of memory 108 b, and 2NICs 108 c, the rules may require that all of these resources 108 besourced from the same server 112. Additionally or alternatively, VM 104may require splitting resources 108 among multiple servers 112, but suchsplitting may need to conform with certain restrictions. For example,resources 108 for VM 104 may be able to be split between two servers112. Default rules may apply. For example, a default rule may requirethat all resources 108 for a given VM 104 must come from the same server112.

An affinity rule may restrict assignment of resources 108 for aparticular VM 104 (or a particular type of VM 104). For example, anaffinity rule may require that certain VMs 104 be instantiated on (thatis, consume resources from) the same server 112 or chassis 110. Forexample, if VNF 102 uses six MCM VMs 104 a, an affinity rule may dictatethat those six MCM VMs 104 a be instantiated on the same server 112 (orchassis 110). As another example, if VNF 102 uses MCM VMs 104 a, ASM VMs104 b, and a third type of VMs 104, an affinity rule may dictate that atleast the MCM VMs 104 a and the ASM VMs 104 b be instantiated on thesame server 112. (or chassis 110). Affinity rules may restrictassignment of resources 108 based on the identity or type of resource108, VNF 102, VM 104, chassis 110, server 112, or any combinationthereof.

An anti-affinity rule may restrict assignment of resources 108 for aparticular VM 104 (or a particular type of VM 104). In contrast to anaffinity rule—which may require that certain VMs 104 be instantiated onthe same server 112 or chassis 110—an anti-affinity rule requires thatcertain VMs 104 be instantiated on different servers 112 (or differentchasses 110). For example, an anti-affinity rule may require that MCM VM104 a be instantiated on a particular server 112 that does not containany ASM VMs 104 b. As another example, an anti-affinity rule may requirethat MCM VMs 104 a for a first VNF 102 be instantiated on a differentserver 112 (or chassis 110) than MCM VMs 104 a for a second VNF 102.Anti-affinity rules may restrict assignment of resources 108 based onthe identity or type of resource 108, VNF 102, VM 104, chassis 110,server 112, or any combination thereof.

Within these constraints, resources 108 of hardware platform 106 may beassigned to be used to instantiate VMs 104, which in turn may be used toinstantiate VNFs 102, which in turn may be used to establish sessions.The different combinations for how such resources 108 may be assignedmay vary in complexity and efficiency. For example, differentassignments may have different limits of the number of sessions that canbe established given a particular hardware platform 106.

For example, consider a session that may require gateway VNF 102 a andPCRF VNF 102 b. Gateway VNF 102 a may require five VMs 104 instantiatedon the same server 112, and PCRF VNF 102 b may require two VMs 104instantiated on the same server 112. (Assume, for this example, that noaffinity or anti-affinity rules restrict whether VMs 104 for PCRF VNF102 b may or must be instantiated on the same or different server 112than VMs 104 for gateway VNF 102 a.) In this example, each of twoservers 112 may have sufficient resources 108 to support 10 VMs 104. Toimplement sessions using these two servers 112, first server 112 may beinstantiated with 10 VMs 104 to support two instantiations of gatewayVNF 102 a, and second server 112 may be instantiated with 9 VMs: fiveVMs 104 to support one instantiation of gateway VNF 102 a and four VMs104 to support two instantiations of PCRF VNF 102 b. This may leave theremaining resources 108 that could have supported the tenth VM 104 onsecond server 112 unused (and unusable for an instantiation of either agateway VNF 102 a or a PCRF VNF 102 b). Alternatively, first server 112may be instantiated with 10 VMs 104 for two instantiations of gatewayVNF 102 a and second server 112 may be instantiated with 10 VMs 104 forfive instantiations of PCRF VNF 102 b, using all available resources 108to maximize the number of VMs 104 instantiated.

Consider, further, how many sessions each gateway VNF 102 a and eachPCRF VNF 102 b may support. This may factor into which assignment ofresources 108 is more efficient. For example, consider if each gatewayVNF 102 a supports two million sessions, and if each PCRF VNF 102 bsupports three million sessions. For the first configuration—three totalgateway VNFs 102 a (which satisfy the gateway requirement for sixmillion sessions) and two total PCRF VNFs 102 b (which satisfy the PCRFrequirement for six million sessions)—would support a total of sixmillion sessions. For the second configuration—two total gateway VNFs102 a (which satisfy the gateway requirement for four million sessions)and five total PCRF VNFs 102 b (which satisfy the PCRF requirement for15 million sessions)—would support a total of four million sessions.Thus, while the first configuration may seem less efficient looking onlyat the number of available resources 108 used (as resources 108 for thetenth possible VM 104 are unused), the second configuration is actuallymore efficient from the perspective of being the configuration that cansupport more the greater number of sessions.

To solve the problem of determining a capacity (or, number of sessions)that can be supported by a given hardware platform 105, a givenrequirement for VNFs 102 to support a session, a capacity for the numberof sessions each VNF 102 (e.g., of a certain type) can support, a givenrequirement for VMs 104 for each VNF 102 (e.g., of a certain type), agive requirement for resources 108 to support each VM 104 (e.g., of acertain type), rules dictating the assignment of resources 108 to one ormore VMs 104 (e.g., affinity and anti-affinity rules), the chasses 110and servers 112 of hardware platform 106, and the individual resources108 of each chassis 110 or server 112 (e.g., of a certain type), aninteger programming problem may be formulated.

First, a plurality of index sets may be established. For example, indexset L may include the set of chasses 110. For example, if a systemallows up to 6 chasses 110, this set may be:

L=(1,2,3,4,5,6),

where l is an element of L.

Another index set J may include the set of servers 112. For example, ifa system allows up to 16 servers 112 per chassis 110, this set may be:

J={1,2,3, . . . ,16},

where j is an element of J.

As another example, index set K having at least one element k mayinclude the set of VNFs 102 that may be considered. For example, thisindex set may include all types of VNFs 102 that may be used toinstantiate a service. For example, let

K={GW,PCRF}

where GW represents gateway VNFs 102 a and PCRF represents PCRF VNFs 102b.

Another index set I(k) may equal the set of VMs 104 for a VNF 102 k.Thus, let

I(GW)=(MCM,ASM,IOM,WSM,CCM,DCM)

represent VMs 104 for gateway VNF 102 a, where MCM represents MCM VM 104a, ASM represents ASM VM 104 b, and each of IOM, WSM, CCM, and DCMrepresents a respective type of VM 104. Further, let

I(PCRF)=(DEP,DIR,POL,SES,MAN)

represent VMs 104 for PCRF VNF 102 b, where DEP represents DEP VM 104 cand each of DIR, POL, SES, and MAN represent a respective type of VM104.

Another index set V may include the set of possible instances of a givenVM 104. For example, if a system allows up to 20 instances of VMs 102,this set may be:

V=(1,2,3, . . . ,20),

where v is an element of V.

In addition to the sets, the integer programming problem may includeadditional data. The characteristics of VNFs 102, VMs 104, chasses 110,or servers 112 may be factored into the problem. This data may bereferred to as parameters. For example, for given VNF 102 k, the numberof sessions that VNF 102 k can support may be defined as a functionS(k). In an aspect, for an element k of set K, this parameter may berepresented by

S(k)>=0;

is a measurement of the number of sessions k can support. Returning tothe earlier example where gateway VNF 102 a may support 2 millionsessions, then this parameter may be

S(GW)=2,000,000.

VM 104 modularity may be another parameter in the integer programmingproblem. VM 104 modularity may represent the VM 104 requirement for atype of VNF 102. For example, for k that is an element of set K and ithat is an element of set I, each instance of VNF k may require M(k, i)instances of VMs 104. For example, recall the example where

I(GW)=(MCM,ASM,IOM,WSM,CCM,DCM).

In an example, M(GW, I(GW)) may be the set that indicates the number ofeach type of VM 104 that may be required to instantiate gateway VNF 102a. For example,

M(GW,I(GW))=(2,16,4,4,2,4)

may indicate that one instantiation of gateway VNF 102 a may require twoinstantiations of MCM VMs 104 a, 16 instantiations of ACM VM 104 b, fourinstantiations of IOM VM 104, four instantiations of WSM VM 104, twoinstantiations of CCM VM 104, and four instantiations of DCM VM 104.

Another parameter may indicate the capacity of hardware platform 106.For example, a parameter C may indicate the number of vCPUs 108 arequired for each VM 104 type i and for each VNF 102 type k. Forexample, this may include the parameter

C(k,i).

For example, if MCM VM 104 a for gateway VNF 102 a requires 20 vCPUs 108a, this may be represented as

C(GW,MCM)=20.

However, given the complexity of the integer programming problem—thenumerous variables and restrictions that must be satisfied—implementingan algorithm that may be used to solve the integer programming problemefficiently, without sacrificing optimality, may be difficult.

FIG. 4 illustrates a functional block diagram depicting one example ofan LTE-EPS network architecture 400 that may be at least partiallyimplemented as an SDN. Network architecture 400 disclosed herein isreferred to as a modified LTE-EPS architecture 400 to distinguish itfrom a traditional LTE-EPS architecture.

An example modified LTE-EPS architecture 400 is based at least in parton standards developed by the 3rd Generation Partnership Project (3GPP),with information available at www.3Dpp.org. LTE-EPS network architecture400 may include an access network 402, a core network 404, e.g., an EPCor Common BackBone (CBB) and one or more external networks 406,sometimes referred to as PDN or peer entities. Different externalnetworks 406 can be distinguished from each other by a respectivenetwork identifier, e.g., a label according to DNS naming conventionsdescribing an access point to the PDN. Such labels can be referred to asAccess Point Names (APN). External networks 406 can include one or moretrusted and non-trusted external networks such as an internet protocol(IP) network 408, an IP multimedia subsystem (IMS) network 410, andother networks 412, such as a service network, a corporate network, orthe like. In an aspect, access network 402, core network 404, orexternal network 405 may include or communicate with network 100.

Access network 402 can include an LTE network architecture sometimesreferred to as Evolved Universal mobile Telecommunication systemTerrestrial Radio Access (E UTRA) and evolved UMTS Terrestrial RadioAccess Network (E-UTRAN). Broadly, access network 402 can include one ormore communication devices, commonly referred to as UE 414, and one ormore wireless access nodes, or base stations 416 a, 416 b. Duringnetwork operations, at least one base station 416 communicates directlywith UE 414. Base station 416 can be an evolved Node B (e-NodeB), withwhich UE 414 communicates over the air and wirelessly. UEs 414 caninclude, without limitation, wireless devices, e.g., satellitecommunication systems, portable digital assistants (PDAs), laptopcomputers, tablet devices and other mobile devices (e.g., cellulartelephones, smart appliances, and so on). UEs 414 can connect to eNBs416 when UE 414 is within range according to a corresponding wirelesscommunication technology.

UE 414 generally runs one or more applications that engage in a transferof packets between UE 414 and one or more external networks 406. Suchpacket transfers can include one of downlink packet transfers fromexternal network 406 to UE 414, uplink packet transfers from UE 414 toexternal network 406 or combinations of uplink and downlink packettransfers. Applications can include, without limitation, web browsing,VoIP, streaming media and the like. Each application can pose differentQuality of Service (QoS) requirements on a respective packet transfer.Different packet transfers can be served by different bearers withincore network 404, e.g., according to parameters, such as the QoS.

Core network 404 uses a concept of bearers, e.g., EPS bearers, to routepackets, e.g., IP traffic, between a particular gateway in core network404 and UE 414. A bearer refers generally to an IP packet flow with adefined QoS between the particular gateway and UE 414. Access network402, e.g., E UTRAN, and core network 404 together set up and releasebearers as required by the various applications. Bearers can beclassified in at least two different categories: (i) minimum guaranteedbit rate bearers, e.g., for applications, such as VoIP; and (ii)non-guaranteed bit rate bearers that do not require guarantee bit rate,e.g., for applications, such as web browsing.

In one embodiment, the core network 404 includes various networkentities, such as MME 418, SGW 420, Home Subscriber Server (HSS) 422,Policy and Charging Rules Function (PCRF) 424 and PGW 426. In oneembodiment, MME 418 comprises a control node performing a controlsignaling between various equipment and devices in access network 402and core network 404. The protocols running between UE 414 and corenetwork 404 are generally known as Non-Access Stratum (NAS) protocols.

For illustration purposes only, the terms MME 418, SGW 420, HSS 422 andPGW 426, and so on, can be server devices, but may be referred to in thesubject disclosure without the word “server.” It is also understood thatany form of such servers can operate in a device, system, component, orother form of centralized or distributed hardware and software. It isfurther noted that these terms and other terms such as bearer pathsand/or interfaces are terms that can include features, methodologies,and/or fields that may be described in whole or in part by standardsbodies such as the 3GPP. It is further noted that some or allembodiments of the subject disclosure may in whole or in part modify,supplement, or otherwise supersede final or proposed standards publishedand promulgated by 3GPP.

According to traditional implementations of LTE-EPS architectures, SGW420 routes and forwards all user data packets. SGW 420 also acts as amobility anchor for user plane operation during handovers between basestations, e.g., during a handover from first eNB 416 a to second eNB 416b as may be the result of UE 414 moving from one area of coverage, e.g.,cell, to another. SGW 420 can also terminate a downlink data path, e.g.,from external network 406 to UE 414 in an idle state, and trigger apaging operation when downlink data arrives for UE 414. SGW 420 can alsobe configured to manage and store a context for UE 414, e.g., includingone or more of parameters of the IP bearer service and network internalrouting information. In addition, SGW 420 can perform administrativefunctions, e.g., in a visited network, such as collecting informationfor charging (e.g., the volume of data sent to or received from theuser), and/or replicate user traffic, e.g., to support a lawfulinterception. SGW 420 also serves as the mobility anchor forinterworking with other 3GPP technologies such as universal mobiletelecommunication system (UMTS).

At any given time, UE 414 is generally in one of three different states:detached, idle, or active. The detached state is typically a transitorystate in which UE 414 is powered on but is engaged in a process ofsearching and registering with network 402. In the active state, UE 414is registered with access network 402 and has established a wirelessconnection, e.g., radio resource control (RRC) connection, with eNB 416.Whether UE 414 is in an active state can depend on the state of a packetdata session, and whether there is an active packet data session. In theidle state, UE 414 is generally in a power conservation state in whichUE 414 typically does not communicate packets. When UE 414 is idle, SGW420 can terminate a downlink data path, e.g., from one peer entity 406,and triggers paging of UE 414 when data arrives for UE 414. If UE 414responds to the page, SGW 420 can forward the IP packet to eNB 416 a.

HSS 422 can manage subscription-related information for a user of UE414. For example, tHSS 422 can store information such as authorizationof the user, security requirements for the user, quality of service(QoS) requirements for the user, etc. HSS 422 can also hold informationabout external networks 406 to which the user can connect, e.g., in theform of an APN of external networks 406. For example, MME 418 cancommunicate with HSS 422 to determine if UE 414 is authorized toestablish a call, e.g., a voice over IP (VoIP) call before the call isestablished.

PCRF 424 can perform QoS management functions and policy control. PCRF424 is responsible for policy control decision-making, as well as forcontrolling the flow-based charging functionalities in a policy controlenforcement function (PCEF), which resides in PGW 426. PCRF 424 providesthe QoS authorization, e.g., QoS class identifier and bit rates thatdecide how a certain data flow will be treated in the PCEF and ensuresthat this is in accordance with the user's subscription profile.

PGW 426 can provide connectivity between the UE 414 and one or more ofthe external networks 406. In illustrative network architecture 400, PGW426 can be responsible for IP address allocation for UE 414, as well asone or more of QoS enforcement and flow-based charging, e.g., accordingto rules from the PCRF 424. PGW 426 is also typically responsible forfiltering downlink user IP packets into the different QoS-based bearers.In at least some embodiments, such filtering can be performed based ontraffic flow templates. PGW 426 can also perform QoS enforcement, e.g.,for guaranteed bit rate bearers. PGW 426 also serves as a mobilityanchor for interworking with non-3GPP technologies such as CDMA2000.

Within access network 402 and core network 404 there may be variousbearer paths/interfaces, e.g., represented by solid lines 428 and 430.Some of the bearer paths can be referred to by a specific label. Forexample, solid line 428 can be considered an S1-U bearer and solid line432 can be considered an S5/S8 bearer according to LTE-EPS architecturestandards. Without limitation, reference to various interfaces, such asS1, X2, S5, S8, S11 refer to EPS interfaces. In some instances, suchinterface designations are combined with a suffix, e.g., a “U” or a “C”to signify whether the interface relates to a “User plane” or a “Controlplane.” In addition, the core network 404 can include various signalingbearer paths/interfaces, e.g., control plane paths/interfacesrepresented by dashed lines 430, 434, 436, and 438. Some of thesignaling bearer paths may be referred to by a specific label. Forexample, dashed line 430 can be considered as an Sl-MME signalingbearer, dashed line 434 can be considered as an S11 signaling bearer anddashed line 436 can be considered as an S6a signaling bearer, e.g.,according to LTE-EPS architecture standards. The above bearer paths andsignaling bearer paths are only illustrated as examples and it should benoted that additional bearer paths and signaling bearer paths may existthat are not illustrated.

Also shown is a novel user plane path/interface, referred to as theS1-U+ interface 466. In the illustrative example, the S1-U+ user planeinterface extends between the eNB 416 a and PGW 426. Notably. S1-U+path/interface does not include SGW 420, a node that is otherwiseinstrumental in configuring and/or managing packet forwarding betweeneNB 416 a and one or more external networks 406 by way of PGW 426. Asdisclosed herein, the S1-U+ path/interface facilitates autonomouslearning of peer transport layer addresses by one or more of the networknodes to facilitate a self-configuring of the packet forwarding path. Inparticular, such self-configuring can be accomplished during handoversin most scenarios so as to reduce any extra signaling load on the S/PGWs420, 426 due to excessive handover events.

In some embodiments, PGW 426 is coupled to storage device 440, shown inphantom. Storage device 440 can be integral to one of the network nodes,such as PGW 426, for example, in the form of internal memory and/or diskdrive. It is understood that storage device 440 can include registerssuitable for storing address values. Alternatively or in addition,storage device 440 can be separate from PGW 426, for example, as anexternal hard drive, a flash drive, and/or network storage.

Storage device 440 selectively stores one or more values relevant to theforwarding of packet data. For example, storage device 440 can storeidentities and/or addresses of network entities, such as any of networknodes 418, 420, 422, 424, and 426, eNBs 416 and/or UE 414. In theillustrative example, storage device 440 includes a first storagelocation 442 and a second storage location 444. First storage location442 can be dedicated to storing a Currently Used Downlink address value442. Likewise, second storage location 444 can be dedicated to storing aDefault Downlink Forwarding address value 444. PGW 426 can read and/orwrite values into either of storage locations 442, 444, for example,managing Currently Used Downlink Forwarding address value 442 andDefault Downlink Forwarding address value 444 as disclosed herein.

In some embodiments, the Default Downlink Forwarding address for eachEPS bearer is the SGW S5-U address for each EPS Bearer. The CurrentlyUsed Downlink Forwarding address” for each EPS bearer in PGW 426 can beset every time when PGW 426 receives an uplink packet, e.g., a GTP-Uuplink packet, with a new source address for a corresponding EPS bearer.When UE 414 is in an idle state, the “Current Used Downlink Forwardingaddress” field for each EPS bearer of UE 414 can be set to a “null” orother suitable value.

In some embodiments, the Default Downlink Forwarding address is onlyupdated when PGW 426 receives a new SGW S5-U address in a predeterminedmessage or messages. For example, the Default Downlink Forwardingaddress is only updated when PGW 426 receives one of a Create SessionRequest, Modify Bearer Request and Create Bearer Response messages fromSGW 420.

As values 442, 444 can be maintained and otherwise manipulated on a perbearer basis, it is understood that the storage locations can take theform of tables, spreadsheets, lists, and/or other data structuresgenerally well understood and suitable for maintaining and/or otherwisemanipulate forwarding addresses on a per bearer basis.

It should be noted that access network 402 and core network 404 areillustrated in a simplified block diagram in FIG. 4. In other words,either or both of access network 402 and the core network 404 caninclude additional network elements that are not shown, such as variousrouters, switches and controllers. In addition, although FIG. 4illustrates only a single one of each of the various network elements,it should be noted that access network 402 and core network 404 caninclude any number of the various network elements. For example, corenetwork 404 can include a pool (i.e., more than one) of MMEs 418, SGWs420 or PGWs 426.

In the illustrative example, data traversing a network path between UE414, eNB 416 a. SGW 420, PGW 426 and external network 406 may beconsidered to constitute data transferred according to an end-to-end IPservice. However, for the present disclosure, to properly performestablishment management in LTE-EPS network architecture 40X), the corenetwork, data bearer portion of the end-to-end IP service is analyzed.

An establishment may be defined herein as a connection set up requestbetween any two elements within LTE-EPS network architecture 400. Theconnection set up request may be for user data or for signaling. Afailed establishment may be defined as a connection set up request thatwas unsuccessful. A successful establishment may be defined as aconnection set up request that was successful.

In one embodiment, a data bearer portion comprises a first portion(e.g., a data radio bearer 446) between UE 414 and eNB 416 a, a secondportion (e.g., an S1 data bearer 428) between eNB 416 a and SGW 420, anda third portion (e.g., an S5/S8 bearer 432) between SGW 420 and PGW 426.Various signaling bearer portions are also illustrated in FIG. 4. Forexample, a first signaling portion (e.g., a signaling radio bearer 448)between UE 414 and eNB 416 a, and a second signaling portion (e.g., Slsignaling bearer 430) between eNB 416 a and MME 418.

In at least some embodiments, the data bearer can include tunneling,e.g., IP tunneling, by which data packets can be forwarded in anencapsulated manner, between tunnel endpoints. Tunnels. or tunnelconnections can be identified in one or more nodes of network 100, e.g.,by one or more of tunnel endpoint identifiers, an IP address and a userdatagram protocol port number. Within a particular tunnel connection,payloads, e.g., packet data, which may or may not include protocolrelated information, are forwarded between tunnel endpoints.

An example of first tunnel solution 450 includes a first tunnel 452 abetween two tunnel endpoints 454 a and 456 a, and a second tunnel 452 bbetween two tunnel endpoints 454 b and 456 b. In the illustrativeexample, first tunnel 452 a is established between eNB 416 a and SGW420. Accordingly, first tunnel 452 a includes a first tunnel endpoint454 a corresponding to an S1-U address of eNB 416 a (referred to hereinas the eNB S1-U address), and second tunnel endpoint 456 a correspondingto an S I-U address of SGW 420 (referred to herein as the SGW S1-Uaddress). Likewise, second tunnel 452 b includes first tunnel endpoint454 b corresponding to an S5-U address of SGW 420 (referred to herein asthe SGW S5-U address), and second tunnel endpoint 456 b corresponding toan S5-U address of PGW 426 (referred to herein as the PGW S5-U address).

In at least some embodiments, first tunnel solution 450 is referred toas a two tunnel solution, e.g., according to the GPRS Tunneling ProtocolUser Plane (GTPv1-U based), as described in 3GPP specification TS29.281, incorporated herein in its entirety. It is understood that oneor more tunnels are permitted between each set of tunnel end points. Forexample, each subscriber can have one or more tunnels, e.g., one foreach PDP context that they have active, as well as possibly havingseparate tunnels for specific connections with different quality ofservice requirements, and so on.

An example of second tunnel solution 458 includes a single or directtunnel 460 between tunnel endpoints 462 and 464. In the illustrativeexample, direct tunnel 460 is established between eNB 416 a and PGW 426,without subjecting packet transfers to processing related to SGW 420.Accordingly, direct tunnel 460 includes first tunnel endpoint 462corresponding to the eNB S1-U address, and second tunnel endpoint 464corresponding to the PGW S5-U address. Packet data received at eitherend can be encapsulated into a payload and directed to the correspondingaddress of the other end of the tunnel. Such direct tunneling avoidsprocessing. e.g., by SGW 420 that would otherwise relay packets betweenthe same two endpoints, e.g., according to a protocol, such as the GTP-Uprotocol.

In some scenarios, direct tunneling solution 458 can forward user planedata packets between eNB 416 a and PGW 426, by way of SGW 420. That is,SGW 420 can serve a relay function, by relaying packets between twotunnel endpoints 416 a, 426. In other scenarios, direct tunnelingsolution 458 can forward user data packets between eNB 416 a and PGW426, by way of the S1 U+ interface, thereby bypassing SGW 420.

Generally, UE 414 can have one or more bearers at any one time. Thenumber and types of bearers can depend on applications, defaultrequirements, and so on. It is understood that the techniques disclosedherein, including the configuration, management and use of varioustunnel solutions 450, 458, can be applied to the bearers on anindividual bases. That is, if user data packets of one bearer, say abearer associated with a VoIP service of UE 414, then the forwarding ofall packets of that bearer are handled in a similar manner. Continuingwith this example, the same UE 414 can have another bearer associatedwith it through the same eNB 416 a. This other bearer, for example, canbe associated with a relatively low rate data session forwarding userdata packets through core network 404 simultaneously with the firstbearer. Likewise, the user data packets of the other bearer are alsohandled in a similar manner, without necessarily following a forwardingpath or solution of the first bearer. Thus, one of the bearers may beforwarded through direct tunnel 458; whereas, another one of the bearersmay be forwarded through a two-tunnel solution 450.

FIG. 5 depicts an exemplary diagrammatic representation of a machine inthe form of a computer system 500) within which a set of instructions,when executed, may cause the machine to perform any one or more of themethods described above. One or more instances of the machine canoperate, for example, as processor 302, UE 414, eNB 416, MME 418, SGW420, HSS 422, PCRF 424, PGW 426 and other devices of FIGS. 1, 2, and 4.In some embodiments, the machine may be connected (e.g., using a network502) to other machines. In a networked deployment, the machine mayoperate in the capacity of a server or a client user machine in aserver-client user network environment, or as a peer machine in apeer-to-peer (or distributed) network environment.

The machine may comprise a server computer, a client user computer, apersonal computer (PC), a tablet, a smart phone, a laptop computer, adesktop computer, a control system, a network router, switch or bridge,or any machine capable of executing a set of instructions (sequential orotherwise) that specify actions to be taken by that machine. It will beunderstood that a communication device of the subject disclosureincludes broadly any electronic device that provides voice, video ordata communication. Further, while a single machine is illustrated, theterm “machine” shall also be taken to include any collection of machinesthat individually or jointly execute a set (or multiple sets) ofinstructions to perform any one or more of the methods discussed herein.

Computer system 500 may include a processor (or controller) 504 (e.g., acentral processing unit (CPU)), a graphics processing unit (GPU, orboth), a main memory 506 and a static memory 508, which communicate witheach other via a bus 510. The computer system 500 may further include adisplay unit 512 (e.g., a liquid crystal display (LCD), a flat panel, ora solid state display). Computer system 500 may include an input device514 (e.g., a keyboard), a cursor control device 516 (e.g., a mouse), adisk drive unit 518, a signal generation device 520 (e.g., a speaker orremote control) and a network interface device 522. In distributedenvironments, the embodiments described in the subject disclosure can beadapted to utilize multiple display units 512 controlled by two or morecomputer systems 500. In this configuration, presentations described bythe subject disclosure may in part be shown in a first of display units512, while the remaining portion is presented in a second of displayunits 512.

The disk drive unit 518 may include a tangible computer-readable storagemedium 524 on which is stored one or more sets of instructions (e.g.,software 526) embodying any one or more of the methods or functionsdescribed herein, including those methods illustrated above.Instructions 526 may also reside, completely or at least partially,within main memory 506, static memory 508, or within processor 504during execution thereof by the computer system 500. Main memory 506 andprocessor 504 also may constitute tangible computer-readable storagemedia.

As shown in FIG. 6, telecommunication system 600 may include wirelesstransmit/receive units (WTRUs) 602, a RAN 604, a core network 606, apublic switched telephone network (PSTN) 608, the Internet 610, or othernetworks 612, though it will be appreciated that the disclosed examplescontemplate any number of WTRUs, base stations, networks, or networkelements. Each WTRU 602 may be any type of device configured to operateor communicate in a wireless environment. For example, a WTRU maycomprise drone 102, a mobile device, network device 300, or the like, orany combination thereof. By way of example, WTRUs 602 may be configuredto transmit or receive wireless signals and may include a UE, a mobilestation, a mobile device, a fixed or mobile subscriber unit, a pager, acellular telephone, a PDA, a smartphone, a laptop, a netbook, a personalcomputer, a wireless sensor, consumer electronics, or the like. WTRUs602 may be configured to transmit or receive wireless signals over anair interface 614.

Telecommunication system 600 may also include one or more base stations616. Each of base stations 616 may be any type of device configured towirelessly interface with at least one of the WTRUs 602 to facilitateaccess to one or more communication networks, such as core network 606.PTSN 608, Internet 610, or other networks 612. By way of example, basestations 616 may be a base transceiver station (BTS), a Node-B, an eNodeB, a Home Node B, a Home eNode B, a site controller, an access point(AP), a wireless router, or the like. While base stations 616 are eachdepicted as a single element, it will be appreciated that base stations616 may include any number of interconnected base stations or networkelements.

RAN 604 may include one or more base stations 616, along with othernetwork elements (not shown), such as a base station controller (BSC), aradio network controller (RNC), or relay nodes. One or more basestations 616 may be configured to transmit or receive wireless signalswithin a particular geographic region, which may be referred to as acell (not shown). The cell may further be divided into cell sectors. Forexample, the cell associated with base station 616 may be divided intothree sectors such that base station 616 may include three transceivers:one for each sector of the cell. In another example, base station 616may employ multiple-input multiple-output (MIMO) technology and,therefore, may utilize multiple transceivers for each sector of thecell.

Base stations 616 may communicate with one or more of WTRUs 602 over airinterface 614, which may be any suitable wireless communication link(e.g., RF, microwave, infrared (IR), ultraviolet (UV), or visiblelight). Air interface 614 may be established using any suitable radioaccess technology (RAT).

More specifically, as noted above, telecommunication system 600 may be amultiple access system and may employ one or more channel accessschemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, or the like. Forexample, base station 616 in RAN 604 and WTRUs 602 connected to RAN 604may implement a radio technology such as Universal MobileTelecommunications System (UMTS) Terrestrial Radio Access (UTRA) thatmay establish air interface 614 using wideband CDMA (WCDMA). WCDMA mayinclude communication protocols, such as High-Speed Packet Access (HSPA)or Evolved HSPA (HSPA+). HSPA may include High-Speed Downlink PacketAccess (HSDPA) or High-Speed Uplink Packet Access (HSUPA).

As another example base station 616 and WTRUs 602 that are connected toRAN 604 may implement a radio technology such as Evolved UMTSTerrestrial Radio Access (E-UTRA), which may establish air interface 614using LTE or LTE-Advanced (LTE-A).

Optionally base station 616 and WTRUs 602 connected to RAN 604 mayimplement radio technologies such as IEEE 602.16 (i.e., WorldwideInteroperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1×,CDMA2000 EV-DO. Interim Standard 2000 (IS-2000), Interim Standard 95(IS-95), Interim Standard 856 (IS-856), GSM, Enhanced Data rates for GSMEvolution (EDGE). GSM EDGE (GERAN), or the like.

Base station 616 may be a wireless router, Home Node B. Home eNode B, oraccess point, for example, and may utilize any suitable RAT forfacilitating wireless connectivity in a localized area, such as a placeof business, a home, a vehicle, a campus, or the like. For example, basestation 616 and associated WTRUs 602 may implement a radio technologysuch as IEEE 602.11 to establish a wireless local area network (WLAN).As another example, base station 616 and associated WTRUs 602 mayimplement a radio technology such as IEEE 602.15 to establish a wirelesspersonal area network (WPAN). In yet another example, base station 616and associated WTRUs 602 may utilize a cellular-based RAT (e.g., WCDMA.CDMA2000, GSM, LTE, LTE-A, etc.) to establish a picocell or femtocell.As shown in FIG. 6, base station 616 may have a direct connection toInternet 610. Thus, base station 616 may not be required to accessInternet 610 via core network 606.

RAN 604 may be in communication with core network 606, which may be anytype of network configured to provide voice, data, applications, and/orvoice over internet protocol (VoIP) services to one or more WTRUs 602.For example, core network 606 may provide call control, billingservices, mobile location-based services, pre-paid calling. Internetconnectivity, video distribution or high-level security functions, suchas user authentication. Although not shown in FIG. 6, it will beappreciated that RAN 604 or core network 606 may be in direct orindirect communication with other RANs that employ the same RAT as RAN604 or a different RAT. For example, in addition to being connected toRAN 604, which may be utilizing an E-UTRA radio technology, core network606 may also be in communication with another RAN (not shown) employinga GSM radio technology.

Core network 606 may also serve as a gateway for WTRUs 602 to accessPSTN 608. Internet 610, or other networks 612. PSTN 608 may includecircuit-switched telephone networks that provide plain old telephoneservice (POTS). For LTE core networks, core network 606 may use IMS core614 to provide access to PSTN 608. Internet 610 may include a globalsystem of interconnected computer networks or devices that use commoncommunication protocols, such as the transmission control protocol(TCP), user datagram protocol (UDP), or IP in the TCP/IP internetprotocol suite. Other networks 612 may include wired or wirelesscommunications networks owned or operated by other service providers.For example, other networks 612 may include another core networkconnected to one or more RANs, which may employ the same RAT as RAN 604or a different RAT.

Some or all WTRUs 602 in telecommunication system 600 may includemulti-mode capabilities. That is, WTRUs 602 may include multipletransceivers for communicating with different wireless networks overdifferent wireless links. For example, one or more WTRUs 602 may beconfigured to communicate with base station 616, which may employ acellular-based radio technology, and with base station 616, which mayemploy an IEEE 802 radio technology.

FIG. 7 is an example system 100 including RAN 604 and core network 606.As noted above, RAN 604 may employ an E-UTRA radio technology tocommunicate with WTRUs 602 over air interface 614. RAN 604 may also bein communication with core network 606.

RAN 604 may include any number of eNode-Bs 702 while remainingconsistent with the disclosed technology. One or more eNode-Bs 702 mayinclude one or more transceivers for communicating with the WTRUs 602over air interface 614. Optionally, eNode-Bs 702 may implement MIMOtechnology. Thus, one of eNode-Bs 702, for example, may use multipleantennas to transmit wireless signals to, or receive wireless signalsfrom, one of WTRUs 602.

Each of eNode-Bs 702 may be associated with a particular cell (notshown) and may be configured to handle radio resource managementdecisions, handover decisions, scheduling of users in the uplink ordownlink, or the like. As shown in FIG. 7 eNode-Bs 702 may communicatewith one another over an X2 interface.

Core network 606 shown in FIG. 7 may include a mobility managementgateway or entity (MME) 704, a serving gateway 706, or a packet datanetwork (PDN) gateway 708. While each of the foregoing elements aredepicted as part of core network 606, it will be appreciated that anyone of these elements may be owned or operated by an entity other thanthe core network operator.

MME 704 may be connected to each of eNode-Bs 702 in RAN 604 via an S1interface and may serve as a control node. For example, MME 704 may beresponsible for authenticating users of WTRUs 602, bearer activation ordeactivation, selecting a particular serving gateway during an initialattach of WTRUs 602, or the like. MME 704 may also provide a controlplane function for switching between RAN 604 and other RANs (not shown)that employ other radio technologies, such as GSM or WCDMA.

Serving gateway 706 may be connected to each of eNode-Bs 702 in RAN 604via the S1 interface. Serving gateway 706 may generally route or forwarduser data packets to or from the WTRUs 602. Serving gateway 706 may alsoperform other functions, such as anchoring user planes duringinter-eNode B handovers, triggering paging when downlink data isavailable for WTRUs 602, managing or storing contexts of WTRUs 602, orthe like.

Serving gateway 706 may also be connected to PDN gateway 708, which mayprovide WTRUs 602 with access to packet-switched networks, such asInternet 610, to facilitate communications between WTRUs 602 andIP-enabled devices.

Core network 606 may facilitate communications with other networks. Forexample, core network 606 may provide WTRUs 602 with access tocircuit-switched networks, such as PSTN 608, such as through IMS core614, to facilitate communications between WTRUs 602 and traditionalland-line communications devices. In addition, core network 606 mayprovide the WTRUs 602 with access to other networks 612, which mayinclude other wired or wireless networks that are owned or operated byother service providers.

FIG. 8 depicts an overall block diagram of an example packet-basedmobile cellular network environment, such as a GPRS network as describedherein. In the example packet-based mobile cellular network environmentshown in FIG. 8, there are a plurality of base station subsystems (BSS)800 (only one is shown), each of which comprises a base stationcontroller (BSC) 802 serving a plurality of BTSs, such as BTSs 804, 806,808. BTSs 804, 806, 808 are the access points where users ofpacket-based mobile devices become connected to the wireless network. Inexample fashion, the packet traffic originating from mobile devices istransported via an over-the-air interface to BTS 808, and from BTS 808to BSC 802. Base station subsystems, such as BSS 800, are a part ofinternal frame relay network 810 that can include a service GPRS supportnodes (SGSN), such as SGSN 812 or SGSN 814. Each SGSN 812, 814 isconnected to an internal packet network 816 through which SGSN 812, 814can route data packets to or from a plurality of gateway GPRS supportnodes (GGSN) 818, 820, 822. As illustrated, SGSN 814 and GGSNs 818, 820,822 are part of internal packet network 816. GGSNs 818, 820, 822 mainlyprovide an interface to external IP networks such as PLMN 824, corporateintranets/internets 826, or Fixed-End System (FES) or the publicInternet 828. As illustrated, subscriber corporate network 826 may beconnected to GGSN 820 via a firewall 830. PLMN 824 may be connected toGGSN 820 via a boarder gateway router (BGR) 832. A Remote AuthenticationDial-In User Service (RADIUS) server 834 may be used for callerauthentication when a user calls corporate network 826.

Generally, there may be a several cell sizes in a network, referred toas macro, micro, pico, femto or umbrella cells. The coverage area ofeach cell is different in different environments. Macro cells can beregarded as cells in which the base station antenna is installed in amast or a building above average roof top level. Micro cells are cellswhose antenna height is under average roof top level. Micro cells aretypically used in urban areas. Pico cells are small cells having adiameter of a few dozen meters. Pico cells are used mainly indoors.Femto cells have the same size as pico cells, but a smaller transportcapacity. Femto cells are used indoors, in residential or small businessenvironments. On the other hand, umbrella cells are used to covershadowed regions of smaller cells and fill in gaps in coverage betweenthose cells.

FIG. 9 illustrates an architecture of a typical GPRS network 900 asdescribed herein. The architecture depicted in FIG. 9 may be segmentedinto four groups: users 902, RAN 904, core network 906, and interconnectnetwork 908. Users 902 comprise a plurality of end users, who each mayuse one or more devices 910. Note that device 910 is referred to as amobile subscriber (MS) in the description of network shown in FIG. 9. Inan example, device 910 comprises a communications device (e.g., mobiledevice 102, mobile positioning center 116, network device 300, any ofdetected devices 500, second device 508, access device 604, accessdevice 606, access device 608, access device 610 or the like, or anycombination thereof). Radio access network 904 comprises a plurality ofBSSs such as BSS 912, which includes a BTS 914 and a BSC 916. Corenetwork 906 may include a host of various network elements. Asillustrated in FIG. 9, core network 906 may comprise MSC 918, servicecontrol point (SCP) 920, gateway MSC (GMSC) 922, SGSN 924, home locationregister (HLR) 926, authentication center (AuC) 928, domain name system(DNS) server 930, and GGSN 932. Interconnect network 908 may alsocomprise a host of various networks or other network elements. Asillustrated in FIG. 9, interconnect network 908 comprises a PSTN 934, anFES/Internet 936, a firewall 1038, or a corporate network 940.

An MSC can be connected to a large number of BSCs. At MSC 918, forinstance, depending on the type of traffic, the traffic may be separatedin that voice may be sent to PSTN 934 through GMSC 922, or data may besent to SGSN 924, which then sends the data traffic to GGSN 932 forfurther forwarding.

When MSC 918 receives call traffic, for example, from BSC 916, it sendsa query to a database hosted by SCP 920, which processes the request andissues a response to MSC 918 so that it may continue call processing asappropriate.

HLR 926 is a centralized database for users to register to the GPRSnetwork. HLR 926 stores static information about the subscribers such asthe International Mobile Subscriber Identity (IMSI), subscribedservices, or a key for authenticating the subscriber. HLR 926 alsostores dynamic subscriber information such as the current location ofthe MS. Associated with HLR 926 is AuC 928, which is a database thatcontains the algorithms for authenticating subscribers and includes theassociated keys for encryption to safeguard the user input forauthentication.

In the following, depending on context, “mobile subscriber” or “MS”sometimes refers to the end user and sometimes to the actual portabledevice, such as a mobile device, used by an end user of the mobilecellular service. When a mobile subscriber turns on his or her mobiledevice, the mobile device goes through an attach process by which themobile device attaches to an SGSN of the GPRS network. In FIG. 9, whenMS 910 initiates the attach process by turning on the networkcapabilities of the mobile device, an attach request is sent by MS 910to SGSN 924. The SGSN 924 queries another SGSN, to which MS 910 wasattached before, for the identity of MS 910. Upon receiving the identityof MS 910 from the other SGSN, SGSN 924 requests more information fromMS 910. This information is used to authenticate MS 910 together withthe information provided by HLR 926. Once verified, SGSN 924 sends alocation update to HLR 926 indicating the change of location to a newSGSN, in this case SGSN 924. HLR 926 notifies the old SGSN, to which MS910 was attached before, to cancel the location process for MS 910. HLR926 then notifies SGSN 924 that the location update has been performed.At this time. SGSN 924 sends an Attach Accept message to MS 910, whichin turn sends an Attach Complete message to SGSN 924.

Next, MS 910 establishes a user session with the destination network,corporate network 940, by going through a Packet Data Protocol (PDP)activation process. Briefly, in the process, MS 910 requests access tothe Access Point Name (APN), for example, UPS.com, and SGSN 924 receivesthe activation request from MS 910. SGSN 924 then initiates a DNS queryto learn which GGSN 932 has access to the UPS.com APN. The DNS query issent to a DNS server within core network 906, such as DNS server 930,which is provisioned to map to one or more GGSNs in core network 906.Based on the APN, the mapped GGSN 932 can access requested corporatenetwork 940. SGSN 924 then sends to GGSN 932 a Create PDP ContextRequest message that contains necessary information. GGSN 932 sends aCreate PDP Context Response message to SGSN 924, which then sends anActivate PDP Context Accept message to MS 910.

Once activated, data packets of the call made by MS 910 can then gothrough RAN 904, core network 906, and interconnect network 908, in aparticular FES/Internet 936 and firewall 1038, to reach corporatenetwork 940.

FIG. 10 illustrates a PLMN block diagram view of an example architecturethat may be replaced by a telecommunications system. In FIG. 10, solidlines may represent user traffic signals, and dashed lines may representsupport signaling. MS 1002 is the physical equipment used by the PLMNsubscriber. For example, drone 102, network device 300, the like, or anycombination thereof may serve as MS 1002. MS 1002 may be one of, but notlimited to, a cellular telephone, a cellular telephone in combinationwith another electronic device or any other wireless mobilecommunication device.

MS 1002 may communicate wirelessly with BSS 1004. BSS 1004 contains BSC1006 and a BTS 1008. BSS 1004 may include a single BSC 1006/BTS 1008pair (base station) or a system of BSC/BTS pairs that are part of alarger network. BSS 1004 is responsible for communicating with MS 1002and may support one or more cells. BSS 1004 is responsible for handlingcellular traffic and signaling between MS 1002 and a core network 1010.Typically, BSS 1004 performs functions that include, but are not limitedto, digital conversion of speech channels, allocation of channels tomobile devices, paging, or transmission/reception of cellular signals.

Additionally, MS 1002 may communicate wirelessly with RNS 1012. RNS 1012contains a Radio Network Controller (RNC) 1014 and one or more Nodes B1016. RNS 1012 may support one or more cells. RNS 1012 may also includeone or more RNC 1014/Node B 1016 pairs or alternatively a single RNC1014 may manage multiple Nodes B 1016. RNS 1012 is responsible forcommunicating with MS 1002 in its geographically defined area. RNC 1014is responsible for controlling Nodes B 1016 that are connected to it andis a control element in a UMTS radio access network. RNC 1014 performsfunctions such as, but not limited to, load control, packet scheduling,handover control, security functions, or controlling MS 1002 access tocore network 1010.

An E-UTRA Network (E-UTRAN) 1018 is a RAN that provides wireless datacommunications for MS 1002 and UE 1024. E-UTRAN 1018 provides higherdata rates than traditional UMTS. It is part of the LTE upgrade formobile networks, and later releases meet the requirements of theInternational Mobile Telecommunications (IMT) Advanced and are commonlyknown as a 4G networks. E-UTRAN 1018 may include of series of logicalnetwork components such as E-UTRAN Node B (eNB) 1020 and E-UTRAN Node B(eNB) 1022. E-UTRAN 1018 may contain one or more eNBs. User equipment(UE) 1024 may be any mobile device capable of connecting to E-UTRAN 1018including, but not limited to, a personal computer, laptop, mobiledevice, wireless router, or other device capable of wirelessconnectivity to E-UTRAN 1018. The improved performance of the E-UTRAN1018 relative to a typical UMTS network allows for increased bandwidth,spectral efficiency, and functionality including, but not limited to,voice, high-speed applications, large data transfer or IPTV, while stillallowing for full mobility.

Typically MS 1002 may communicate with any or all of BSS 1004, RNS 1012,or E-UTRAN 1018. In a illustrative system, each of BSS 1004, RNS 1012,and E-UTRAN 1018 may provide MS 1002 with access to core network 1010.Core network 1010 may include of a series of devices that route data andcommunications between end users. Core network 1010 may provide networkservice functions to users in the circuit switched (CS) domain or thepacket switched (PS) domain. The CS domain refers to connections inwhich dedicated network resources are allocated at the time ofconnection establishment and then released when the connection isterminated. The PS domain refers to communications and data transfersthat make use of autonomous groupings of bits called packets. Eachpacket may be routed, manipulated, processed or handled independently ofall other packets in the PS domain and does not require dedicatednetwork resources.

The circuit-switched MGW function (CS-MGW) 1026 is part of core network1010, and interacts with VLR/MSC server 1028 and GMSC server 1030 inorder to facilitate core network 1010 resource control in the CS domain.Functions of CS-MGW 1026 include, but are not limited to, mediaconversion, bearer control, payload processing or other mobile networkprocessing such as handover or anchoring. CS-MGW 1026 may receiveconnections to MS 1002 through BSS 1004 or RNS 1012.

SGSN 1032 stores subscriber data regarding MS 1002 in order tofacilitate network functionality. SGSN 1032 may store subscriptioninformation such as, but not limited to, the IMSI, temporary identities,or PDP addresses. SGSN 1032 may also store location information such as,but not limited to, GGSN address for each GGSN 1034 where an active PDPexists. GGSN 1034 may implement a location register function to storesubscriber data it receives from SGSN 1032 such as subscription orlocation information.

Serving gateway (S-GW) 1036 is an interface which provides connectivitybetween E-UTRAN 1018 and core network 1010. Functions of S-GW 1036include, but are not limited to, packet routing, packet forwarding,transport level packet processing, or user plane mobility anchoring forinter-network mobility. PCRF 1038 uses information gathered from P-GW1036, as well as other sources, to make applicable policy and chargingdecisions related to data flows, network resources or other networkadministration functions. PDN gateway (PDN-GW) 1040 may provideuser-to-services connectivity functionality including, but not limitedto, GPRS/EPC network anchoring, bearer session anchoring and control, orIP address allocation for PS domain connections.

HSS 1042 is a database for user information and stores subscription dataregarding MS 1002 or UE 1024 for handling calls or data sessions.Networks may contain one HSS 1042 or more if additional resources arerequired. Example data stored by HSS 1042 include, but is not limitedto, user identification, numbering or addressing information, securityinformation, or location information. HSS 1042 may also provide call orsession establishment procedures in both the PS and CS domains.

VLR/MSC Server 1028 provides user location functionality. When MS 1002enters a new network location, it begins a registration procedure. A MSCserver for that location transfers the location information to the VLRfor the area. A VLR and MSC server may be located in the same computingenvironment, as is shown by VLR/MSC server 1028, or alternatively may belocated in separate computing environments. A VLR may contain, but isnot limited to, user information such as the IMSI, the Temporary MobileStation Identity (TMSI), the Local Mobile Station identity (LMSI), thelast known location of the mobile station, or the SGSN where the mobilestation was previously registered. The MSC server may containinformation such as, but not limited to, procedures for MS 1002registration or procedures for handover of MS 1002 to a differentsection of core network 1010. GMSC server 1030 may serve as a connectionto alternate GMSC servers for other MSs in larger networks.

EIR 1044 is a logical element which may store the IMEI for MS 1002. Userequipment may be classified as either “white listed” or “black listed”depending on its status in the network. If MS 1002 is stolen and put touse by an unauthorized user, it may be registered as “black listed” inEIR 1044, preventing its use on the network. A MME 1046 is a controlnode which may track MS 1002 or UE 1024 if the devices are idle.Additional functionality may include the ability of MME 1046 to contactidle MS 1002 or UE 1024 if retransmission of a previous session isrequired.

As described herein, a telecommunications system wherein management andcontrol utilizing a software designed network (SDN) and a simple IP arebased, at least in part, on user equipment, may provide a wirelessmanagement and control framework that enables common wireless managementand control, such as mobility management, radio resource management,QoS, load balancing, etc., across many wireless technologies, e.g. LTE,Wi-Fi, and future 5G access technologies; decoupling the mobilitycontrol from data planes to let them evolve and scale independently;reducing network state maintained in the network based on user equipmenttypes to reduce network cost and allow massive scale; shortening cycletime and improving network upgradability; flexibility in creatingend-to-end services based on types of user equipment and applications,thus improve customer experience; or improving user equipment powerefficiency and battery life-especially for simple M2M devices-throughenhanced wireless management.

While examples of a telecommunications system in which emergency alertscan be processed and managed have been described in connection withvarious computing devices/processors, the underlying concepts may beapplied to any computing device, processor, or system capable offacilitating a telecommunications system. The various techniquesdescribed herein may be implemented in connection with hardware orsoftware or, where appropriate, with a combination of both. Thus, themethods and devices may take the form of program code (i.e.,instructions) embodied in concrete, tangible, storage media having aconcrete, tangible, physical structure. Examples of tangible storagemedia include floppy diskettes, CD-ROMs. DVDs, hard drives, or any othertangible machine-readable storage medium (computer-readable storagemedium). Thus, a computer-readable storage medium is not a signal. Acomputer-readable storage medium is not a transient signal. Further, acomputer-readable storage medium is not a propagating signal. Acomputer-readable storage medium as described herein is an article ofmanufacture. When the program code is loaded into and executed by amachine, such as a computer, the machine becomes an device fortelecommunications. In the case of program code execution onprogrammable computers, the computing device will generally include aprocessor, a storage medium readable by the processor (includingvolatile or nonvolatile memory or storage elements), at least one inputdevice, and at least one output device. The program(s) can beimplemented in assembly or machine language, if desired. The languagecan be a compiled or interpreted language, and may be combined withhardware implementations.

The methods and devices associated with a telecommunications system asdescribed herein also may be practiced via communications embodied inthe form of program code that is transmitted over some transmissionmedium, such as over electrical wiring or cabling, through fiber optics,or via any other form of transmission, wherein, when the program code isreceived and loaded into and executed by a machine, such as an EPROM, agate array, a programmable logic device (PLD), a client computer, or thelike, the machine becomes an device for implementing telecommunicationsas described herein. When implemented on a general-purpose processor,the program code combines with the processor to provide a unique devicethat operates to invoke the functionality of a telecommunicationssystem.

While example embodiments have been described in connection with variouscomputing devices/processors, the underlying concepts can be applied toany computing device, processor, or system capable of recording eventsas described herein. The methods and apparatuses for recording andreporting events, or certain aspects or portions thereof, can take theform of program code (i.e., instructions) embodied in tangible storagemedia having a physical structure, such as floppy diskettes, CD-ROMs,hard drives, or any other machine-readable storage medium having aphysical tangible structure (computer-readable storage medium), wherein,when the program code is loaded into and executed by a machine, such asa computer, the machine becomes an apparatus for distributingconnectivity and/or transmission time. A computer-readable storagemedium, as described herein is an article of manufacture, and thus, isnot to be construed as a transitory signal. In the case of program codeexecution on programmable computers, which may, for example, includeserver 40, the computing device will generally include a processor, astorage medium readable by the processor (including volatile andnon-volatile memory and/or storage elements), at least one input device,and at least one output device. The program(s) can be implemented inassembly or machine language, if desired. The language can be a compiledor interpreted language, and combined with hardware implementations

The methods and systems of the present disclosure may be practiced viacommunications embodied in the form of program code that is transmittedover some transmission medium, such as over electrical wiring orcabling, through fiber optics, wherein, when the program code isreceived and loaded into and executed by a machine, such as an EPROM, agate array, a programmable logic device (PLD), a client computer, acontroller, or the like, the machine becomes an apparatus for use inreconfiguration of systems constructed in accordance with the presentdisclosure. When implemented on a general-purpose processor, the programcode combines with the processor to provide a unique apparatus thatoperates to invoke the functionality described herein.

In addition, while a particular feature may have been disclosed withrespect to only one of several implementations, such feature may becombined with one or more other features of the other implementations asmay be desired and advantageous for any given or particular application.Furthermore, to the extent that the terms “includes,” and “including”and variants thereof are used in either the detailed description or theclaims, these terms are intended to be inclusive in a manner similar tothe term “comprising.”

1. A method comprising: Receiving, by an application service layer, arequest for a communication session, the request originating from a userdevice; Developing, by the application service layer, a set ofperformance metrics associated with the request; forwarding, by theapplication service layer, the request to a master service orchestrationlayer, wherein the set of performance metrics is included with therequest; Connecting, by the application service layer, the user deviceto a network to establish a communication session in accordance with therequest and the set of performance metrics.
 2. The method of claim 1wherein the communication session is a request for content.
 3. Themethod of claim 2 wherein the request comprises requesting that themaster service orchestration layer coordinate the content request bycoordinating the provision of the communication session through anetwork core service control layer, an access network service controllayer and a content service control layer.
 4. The method of claim 3further comprises determining a content type and an encoding scheme andforwarding the content type and encoding scheme.
 5. The method of claim4 wherein the requesting step further comprises an accelerationalgorithm.
 6. The method of claim 1 further comprising coordinating, bythe application service layer, with the master services orchestrationlayer to extract network resources to support the request.
 7. The methodof claim 6 wherein the coordinating step works on a per service chain orper application basis to support the request.
 8. The method of claim 6wherein that coordinating step comprises preparing the content to bedelivered via broadcast to the user device.
 9. The method of claim 8wherein the preparing step comprises preparing delivery of the contentbased on one of available network capacity, user demand, serviceoffering, subscription and geographic location.
 10. The method of claim1 wherein the request includes a type of service request for thecommunication session.
 11. The method of claim 10 wherein the forwardingstep comprises a request for resources in which the resources include(i) a first resource associated with a radio access network (RAN)service control layer for a radio access network wherein the RAN servicecontrol layer is in direct communication with the master serviceorchestration layer and wherein the first resource comprises at leastone virtual network function (VNF), (ii) a second resource associatedwith an network service control layer for network core functions andwherein the network service control layer is in direct communicationwith the master service orchestration layer and wherein the secondresource comprises at least one VNF, and (iii) a third resourceassociated with a content service control layer for content and whereinthe content service control layer is in direct communication with themaster service orchestration layer and wherein the third resourcecomprises at least one VNF.
 12. The method of claim 11 wherein theconnecting step comprises establishing the communication session usingthe first resource, the second resource and the third resource byfacilitating direct communications between the RAN service controllayer, the network service control layer and the content service controllayer.
 13. The method of claim 11 further comprising tracking aperformance metric for the communication and adjusting capacity of thesecond resource based on the tracking step.
 14. The method of claim 1further comprising receiving, by the application service layer, currentnetwork status associated with a core network and wherein the set ofperformance metrics identifies network capacity in view of the currentnetwork status.
 15. A method comprising: receiving a request for contentfrom a content network having a content service control layer, whereinthe request includes a request for the content to be broadcast to a userdevice; determining a type of content associated with the request;selecting an encoding scheme for broadcast of the content; coordinatingcommunication between the content service control layer, a network coreservice control layer, and an access network service control layer;instantiating virtual network functions (VNF) to provide sufficientresources for broadcasting content to end users; and broadcasting thecontent to the end users.
 16. The method of claim 15 wherein the requestis received by an application service layer wherein the applicationservice layer determines performance metrics associated with the requestand the request and performance metrics are forwarded to a masterservice orchestration layer.
 17. The method of claim 16 furthercomprising comparing the performance metrics to a current state ofnetwork resources and a number of VNFs instantiated are adjusted basedon the comparing steps.
 18. The method of claim 17 wherein the masterservices orchestration layer and the application service layer work intandem on a per service chain or per application basis to determine thenetwork resources to instantiate the number of VNFs to support thebroadcasting of content.
 19. A method comprising: receiving a requestfor content from a user device; determining access network resources tobe allocated to support the request by an access network control layer;determining network core access resources to be allocated to support therequest by a core access control layer; determining content resources tobe allocated to support the request by a content control layer, whereinthe content resources are based on the content requested by a user;establishing performance metrics associated with the content; assigningaccess network resources, network core access resources, and contentresources to virtual network functions (VNFs); instantiating the VNFs;establishing a communication to deliver the content; and monitoring theperformance metrics.
 20. The method of claim 19 wherein the monitoringstep comprises monitoring an end user experience and comparing the enduser experience to the performance metrics.